Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

indra/newview/llaisapi.cpp (2)

1693-1702: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Extract the deferred-notification block into a helper to avoid duplication.

Both backlog paths contain the identical 8-line coalescing block. A small static helper would keep them in sync and reduce maintenance risk if the notification logic changes.

♻️ Proposed helper extraction

+static void postDeferredNotifyObservers()
+{
+    if (!sAISNotifyObserversPending)
+    {
+        sAISNotifyObserversPending = true;
+        LLAppViewer::instance()->postToMainCoro(
+            []()
+            {
+                gInventory.notifyObservers();
+                sAISNotifyObserversPending = false;
+            });
+    }
+}
+
 // ... then at both backlog sites:
-            if (!sAISNotifyObserversPending)
-            {
-                sAISNotifyObserversPending = true;
-                LLAppViewer::instance()->postToMainCoro(
-                    []()
-                    {
-                        gInventory.notifyObservers();
-                        sAISNotifyObserversPending = false;
-                    });
-            }
+            postDeferredNotifyObservers();

Also applies to: 1763-1772

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@indra/newview/llaisapi.cpp` around lines 1693 - 1702, Extract the duplicated
sAISNotifyObserversPending coalescing logic into a shared static helper near the
existing AIS notification code, including posting the main-coroutine callback
and resetting the flag after gInventory.notifyObservers(). Replace both
backlog-path blocks around the relevant notification handling with calls to this
helper, preserving the current behavior.

---

1843-1848: 🚀 Performance & Scalability | 🔵 Trivial | 💤 Low value

Guard the final deferred notification with the coalescing flag.

When the backlog path already posted a deferred notifyObservers() (flag is still true), this unconditional post queues a second notifyObservers() that will run after the backlog lambda. The second call iterates all observers but processes no changes (IDs already cleared). Checking !sAISNotifyObserversPending avoids the redundant post — the pending backlog lambda will process all accumulated changes since doUpdate() doesn't yield between the backlog post and this final post.

♻️ Proposed fix

-    LLAppViewer::instance()->postToMainCoro(
-        []()
-        {
-            gInventory.notifyObservers();
-        });
+    if (!sAISNotifyObserversPending)
+    {
+        LLAppViewer::instance()->postToMainCoro(
+            []()
+            {
+                gInventory.notifyObservers();
+            });
+    }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@indra/newview/llaisapi.cpp` around lines 1843 - 1848, Guard the final
deferred notification in the surrounding AIS update flow with
!sAISNotifyObserversPending before calling
LLAppViewer::instance()->postToMainCoro. Keep the existing notifyObservers
callback unchanged, and avoid posting it when the backlog path has already
scheduled the pending notification.